Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Act! to Filevine migration

Act! is a desktop CRM and intake system, and Filevine is a cloud case management system. Contacts and intake history move, and open enquiries become leads or cases in Filevine.

FromAct!Desktop
  1. Contacts: Carried across
  2. Documents: Carried across
  3. Emails: Carried across
  4. Notes: Carried across
  5. Calendar: Carried across
  6. Tasks: Carried across
  7. Custom fields: Carried with mapping
  8. Templates: Carried with mapping
  9. Intake: Carried with mapping
ToFilevineCloud
  • 6 carried
  • 3 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Act! to Filevine

Each row is a kind of record Act! holds, whether Filevine has a place for it, and what is planned. On this route six kinds of record carry across and three kinds need mapping.

Records in Act! and their place in Filevine
RecordIn Act!In FilevineWhat is planned
ContactsClients, other parties and referrersHeldContacts, secondary contacts, companies and groups.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeld in partFiles attached to records are kept in an attachments folder beside the database.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails can be recorded in a contact’s history through the Outlook or Gmail link.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldNotes and history entries are kept against each contact.Has a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldActivities: calls, meetings and to-dos with dates.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTo-dos are one kind of activity.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfHeldFields are added through Define Fields and placed on screen layouts.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, report templates and layouts are stored with the database.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partOpportunities move through a sales pipeline; web forms come with the marketing tools.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Carried with mapping

What the plans mean

Carried across
Filevine has a place for this kind of record. It is loaded there and checked against Act!.
Carried with mapping
Filevine holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.

This kind of move

Intake history moves. The pipeline is rebuilt.

Intake data is the front end of a case. A lead in Act! carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where Filevine has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.

Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in Filevine or in the tool that feeds it.

Act! runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Filevine is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

A move off Act! starts with finding the database. Many firms have more than one: a main copy on a server and remote copies that synchronise from laptops. Once the working copy is identified, contacts, companies, groups, notes, history and activities are read from it and matched to the people and matters in the new system. Attached files come from a separate folder.

  1. The database and its attachments

    The desktop edition’s own backup produces a zip file holding the database, attached documents, layouts, document templates, report templates and saved queries. Attachments can be left out of that backup, so a copy made for another purpose may not include them. The extraction is taken from a backup known to include the attachments folder.

  2. Remote copies that synchronise

    Act! lets a laptop carry a remote database that synchronises with the main one. A remote copy that has not synchronised for months holds notes and history nobody else has seen. Before extraction each remote user synchronises a final time, and the main database is treated as the single source.

  3. History is the valuable part

    A plain contact export gives names and addresses. What a firm usually wants to keep is the history: years of calls, meetings and correspondence against each person. History, notes and activities are separate record types linked to contacts, and each one needs a decided home in the destination, usually as dated notes on the client or the matter.

  4. Groups and companies

    Groups are how many Act! users sort their contacts: a Christmas card list, a referrer list, clients of one partner. A contact can sit in several groups and can be linked to a company record. Those memberships become tags, categories or mailing lists in the new system, and the mapping is agreed group by group.

  5. Fields the firm defined

    Act! databases are often customised over many years, with fields added through Define Fields and laid out on custom screens. Some are still in use and some were abandoned long ago. Each defined field is listed with a count of the records that use it, so the firm can choose which ones are worth carrying.

More about moving off Act!

Where it is going

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Filevine on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Act! holds and how it is organised, then agree with you where each kind of record will sit in Filevine. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Filevine and checked against Act!: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Act!, a final pass over a weekend picks up what changed since the trial. Act! is kept read only as the fall-back record.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in Act! and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.

Step 1 of 5

Step 1 of 5: Start with the route

Moving fromAct!
Moving toFilevine

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Act! holds

    What is in it, how its records link, and where each piece would sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. A fixed price in writing

    Set after the analysis, so it reflects what is in your data. You have it before any work starts.

Beyond the data

Setting up Filevine

Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

Act! to Filevine: what firms ask

Can the history against each contact come across?

Usually, as dated notes. History entries, notes and activities are held separately from the contact’s own fields, so they are extracted as their own lists and linked back to the right person. Whether they land on the contact or on a matter depends on how the destination files notes, and that is settled in the analysis.

We have several Act! databases. Which one is moved?

All of them can be read, but they are combined before loading, not after. Act! checks for duplicates on fields the administrator chooses, so two databases may hold the same person under slightly different details. The databases are compared, the overlaps are listed, and the firm decides which record wins.

What happens to documents attached to contacts?

Attached files live in a folder beside the database, with the link held on the contact’s record. They are copied out with those links intact and filed against the matching client or matter in the new system. A file attached to a contact who has several matters needs a rule for where it goes.

Do documents from Act! keep their folders and dates in Filevine?

Filevine stores documents. Docs section with folders. Templated project folders can be set per type. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Act! have a place in Filevine?

On paper, yes: each kind of record Act! holds has a place in Filevine. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Act! data is loaded into Filevine?

Custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. The firm also decides which closed matters and how many versions of a document are in scope.

Where to start

Before and after the move.

Choosing the system comes before a migration. Setting it up and putting AI to work come after.

How we do itDiscovery to rollout, step by step

Act! and Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from Act! to Filevine?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.