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

Data migration route

Act! data to Microsoft SQL Server

Act! is a desktop CRM and intake system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Act! holds and keeps it readable and open to queries.

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

What moves

What moves from Act! to Microsoft SQL Server

Each row is a kind of record Act! holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route five kinds of record carry across and four kinds need mapping.

Records in Act! and their place in Microsoft SQL Server
RecordIn Act!In Microsoft SQL ServerWhat is planned
ContactsClients, other parties and referrersHeldContacts, secondary contacts, companies and groups.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeld in partFiles attached to records are kept in an attachments folder beside the database.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
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 place in partAs message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesHeldNotes and history entries are kept against each contact.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldActivities: calls, meetings and to-dos with dates.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTo-dos are one kind of activity.Has a placeRows with assignee, due date and status.Exported in full
Custom fieldsFields and record types the firm added itselfHeldFields are added through Define Fields and placed on screen layouts.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, report templates and layouts are stored with the database.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partOpportunities move through a sales pipeline; web forms come with the marketing tools.Has a placeEnquiry rows, where the source recorded them.Exported in full

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Act!.
Exported with mapping
Microsoft SQL Server 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

Not a new system. A complete copy the firm can query.

Writing Act! out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Act! as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Act! stays untouched until the copy in Microsoft SQL Server has been checked.

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Act! holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Act! holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against Act!: record counts, totals where Act! holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Act!, the export is run a final time and checked again. There is nothing to go live. Act! is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Structure, permissions and handover

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Act! to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold documents from Act!?

In part. As files in folders with an index table; storing files in the database is possible. What Microsoft SQL Server can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without Act!.

Does everything in Act! have a place in Microsoft SQL Server?

On paper, yes: each kind of record Act! holds has a place in Microsoft SQL Server. 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! is written out to Microsoft SQL Server?

Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Act! to Microsoft SQL Server?

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

We reply within one business day.